This folder is simulating secure offline storage. Whenever you use strong names,
you need to carefully store the private key and only make use of it
to sign assemblies that are ready to be shipped for production.

In the labs, we make use of delay signing. To tell the CLR that your system
is preproduction and that it shouldn't attempt to validate any of your
assembly signatures, you can run sn.exe as follows:

sn -Vr *,<pubkeytoken>

where <pubkeytoken> can be calculated from any assembly with the strong
name you're looking for as follows:

sn -T <assembly>

or it can be pulled from the public key file directly (NOTE: this is the
public key file, not the file with both public and private keys):

sn -t pubkey

to get the public key file from the public/private key file (which is what
you get when you run sn -k), use the following command

sn -p pubprivkey pubkey

the above command tells sn.exe to read pubprivkey and write the public part
ONLY to pubkey, which is what you want to distribute to developers.
